Description

This pull request consolidates all changes from the previous two PRs into a single, clean branch to resolve the merge-order issue encountered earlier.

It combines:

• The global light/dark theme toggle implementation, and
• The subsequent UI consistency and visual stability pass across major components.

The goal of this PR is to deliver the complete, intended UI experience in one mergeable unit, ensuring predictable theming, consistent visual behavior, and improved readability across both light and dark modes - without introducing new features beyond what was already reviewed and approved conceptually.

Type of Change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Code refactoring
• Performance improvement
• UI/UX improvement
• Content update
• Chore/maintenance

Related Issue

Closes #31
It adds the feature brought by PR #64 and also fixes all the conflicts related to it due to recent changes in the codebase.

Changes Made

This PR includes the full, consolidated set of changes from both earlier PRs:

• Added a global light/dark theme toggle using a .dark class strategy.
• Introduced CSS variables (--background, --foreground) as the single source of truth for theming.
• Updated core layout sections (Hero, Features, Navbar, Footer) to rely on theme variables instead of hardcoded colors.
• Fixed color inheritance and layering issues that caused text or components to disappear or lose contrast.
• Normalized hover behavior, borders, shadows, and opacity handling across components.
• Refined Hero section typography, gradients, badges, and pills for consistent visibility in light mode.
• Stabilized carousel cards, navigation buttons, and indicators using simpler, predictable styling rules.
• Unified badge and card styling to maintain visual continuity across sections.
• Cleaned up invalid or conflicting Tailwind classes that caused CSS parsing or rendering issues.
• Improved navbar and footer branding hover interactions for consistent behavior.

No new functionality beyond the previously reviewed changes has been introduced.

Testing Done

Please describe how you tested your changes:

• Tested in development mode (npm run dev)
• Tested production build (npm run build && npm start)
• Tested on multiple browsers (Chrome and Edge)
• Tested on mobile devices/responsive design
• Ran linting (npm run lint)
• Checked for console errors

Screenshots (if applicable)

Mentioned in the previous PRs.

Checklist

IMPORTANT: Please ensure all items are checked before submitting. PRs that don't follow these guidelines may be closed.

• I have read and followed all guidelines in CONTRIBUTING.md
• I have used the correct branch naming convention (feature/, fix/, docs/, etc.)
• My commits follow Conventional Commits format (feat:, fix:, docs:, etc.)
• I have performed a self-review and tested my changes thoroughly
• CRITICAL: I confirm ONLY my intended changes are included (no unrelated changes, debug code, or breaking changes)
• I have updated relevant documentation if needed
• I have tested the production build locally
• My changes are responsive and work on mobile devices

Additional Notes

Any additional information that would be helpful for reviewers?

Hello @akash-kumar-dev.

This PR was created to address a merge-order issue encountered when the earlier PRs were submitted separately.
All changes have now been rebased, consolidated, and verified together to ensure a smooth and conflict-free merge.

Thanks for the review and sorry again for the inconvenience.
I hope all the changes made are proper and won't cause any further problems. If there is any other problems, please let me know, I will fix them.

Thank you!!

Remember: Quality over quantity. A well-tested, properly documented small PR is better than a large, rushed contribution.

For more details, please refer to our Contributing Guidelines.